Set up logic for dual interface wireless IP communication device

ABSTRACT

A communication interface device includes a wireless Internet packet (IP) transceiver and a PCMCIA card electrically connected to the transceiver. Also, a universal serial bus (USB) connector is plugged into a hub that holds the PCMCIA card, with a cord extending from the USB connector and terminating in another USB connector. Accordingly, the device can be engaged with the PCMCIA bay of a user terminal or, if a user terminal has no PCMCIA bay, with a USB receptacle of the user terminal, to establish wireless communication. To simplify set-up, a CD containing all operating system versions of PCMCIA and USB drivers is engaged with the user terminal. The terminal&#39;s operating system is then automatically determined, and only the drivers associated with that operating system are loaded onto the terminal.

This is a continuation of U.S. patent application Ser. No. 09/839,060,filed Apr. 20, 2001, now U.S. Pat. No. 6,889,058, from which priority isclaimed.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to wireless Internet Packet (IP)communication devices having more than one interface format.

2. Description of the Related Art

Networked computing is a powerful tool for business and personal use.With it, the user of a user terminal that communicates with a networksuch as a company's local area network (LAN) or a wide area network(WAN) can access and share data with other terminals in the network.

Most LAN/WANs are implemented by wired connections, i.e., by requiringthat the computers in a network be attached to the network by means ofwires. For convenience and to permit easy movement of user terminalswithin the Network, wireless Networks have been introduced, in whichnetwork communication is established via a wireless radiofrequency (rt)or infrared (IR) link.

As recognized by the present assignee, a wireless communicationinterface can be established by connecting an interface component to auser terminal such as a laptop computer or personal computer. Onceconnected, the interface component can be used to transfer data via thewireless link between the user terminal and the network. As alsorecognized by the present assignee, an interface component must bemechanically configured to engage the user terminal and electricallyconfigured to communicate via the particular wireless link being used.Unfortunately, some potentially preferred interface components, such aspersonal computer memory card interface architecture (PCMCIA) cardswhich are configured for engaging a PCMCIA slot in a laptop computer,might not be engageable with PCs without a PCMCIA card adaptor, becausemany PCs do not have PCMCIA slots. Accordingly, we observe that aseparate interface component that would include a mechanical connectionsuch as a PCMCIA card adaptor or a universal serial bus (USB) connectorwould be required to interface such PCs with the wireless link.

Moreover, while two mechanical connections defining two respectiveinterface formats might be required to link two differently-configureduser terminals to a network, many of the electrical components thatsupport wireless link communication would remain the same for eachterminal. Thus, making separate interface devices for each type of userterminal in the network is wasteful since common communicationcomponents would have to be duplicated in separate devices. Thisincreases manufacturing costs and requires a user of both a networklaptop and a network PC to purchase and use separate interface devices,one for each of his network terminals.

To address the above-noted issues, a dual interface device has beendisclosed in co-pending U.S. patent application Ser. No. 09/833,489,filed Apr. 12, 2001. The present invention recognizes that for such adual interface device, each interface requires a respective softwaredriver tailored to the particular operating system of the computersought to be used. Accordingly, the correct drivers must first be loadedinto the computer, but as recognized herein this requires the user to besufficiently proficient to know what operating system (and perhaps evenwhat version of the operating system) happens to be loaded onto thecomputer. Unfortunately, not all users know what operating system isused by their computer. Furthermore, software drivers are typicallyprovided on compact disks (CDs). This means that to load the drivers forthe dual interface device, a CD must be engaged with the computer.However, the present invention understands that certain computers, e.g.,some types of laptop computers, have only a single PCMCIA slot to whicha CD must be connected when it is desired to establish communicationbetween the CD and computer, thereby preventing simultaneous use of thePCMCIA slot for a dual interface device that might use the PCMCIA formfactor to access the appropriate driver on a CD. Having recognized theabove-noted problem, the present invention provides the solutiondisclosed herein.

SUMMARY OF THE INVENTION

A method is disclosed for enabling a user terminal to use acommunication interface device that has a personal computer memory cardinterface architecture (PCMCIA) interface and a universal serial bus(USB) interface without requiring the user to know the type of operatingsystem used by the terminal or the type of driver that is needed. Themethod includes engaging a storage device with the user terminal, withthe storage device containing plural PCMCIA drivers and plural USBdrivers. Each driver is associated with a respective operating system.The method then automatically determines the type of operating system ofthe user terminal, and automatically loads a PCMCIA driver and a USBdriver onto the user terminal in response. Wireless Internet packet (IP)communication can then be undertaken using the drivers.

In one preferred embodiment, a user set-up prompt can be provided to theuser. Also, if desired a driver directory can be automatically defined.Diagnostic monitoring can also be undertaken after the drivers areloaded. In any case, the acts of determining and loading do not requireuser input regarding a type of operating system on the user terminal.

In another aspect, a computer program product that can be engaged with auser terminal includes plural first communication interface driver meansand plural second communication interface driver means. Each drivermeans is correlated to a respective operating system. Logic means areprovided for determining a type of operating system used by theterminal. Also, logic means that are responsive to the means fordetermining provide at least one first communication interface drivermeans and at least one second communication interface driver means tothe user terminal.

In yet another aspect, a user terminal is disclosed for providingwireless IP communication using an interface device having at leastfirst and second communication interfaces. The terminal includes anoperating system and a computer program that determines the type of theoperating system without receiving any user input indicating the type.In response, the program automatically loads first and second devicedrivers associated with the first and second communication interfaceswithout any user input regarding driver types.

The details of the present invention, both as to its structure andoperation, can best be understood in reference to the accompanyingdrawings, in which like reference numerals refer to like parts.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing the system architecture of thepresent invention;

FIG. 2 is an exploded perspective view of a preferred wireless IPcommunication interface device;

FIG. 3 is a flow chart showing the logic for invoking the appropriatedevice driver;

FIG. 4 is a flow chart showing the operating logic of the system; and

FIG. 5 is a flow chart showing the set up logic of the system.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Referring initially to FIG. 1, a system is shown, generally designated10, that includes a communication interface device 12 engageable with auser terminal 14 potentially having access to a computer program product15 for establishing wireless communication between the terminal 14 and abase station 16 of a wireless network 18. In one non-limiting embodimentused only for illustration purposes, the network 18 can have a broadbandInternet packet (IP) data protocol, such as an i-Burst network made byArraycomm. Such a network can use space division multiple access (SDMA)directional communication principles and has a data transfer rate inexcess of one megabyte per second. The program product 15 can be anysuitable device, such as but not limited to a CD-ROM, floppy disk, etc.As set forth further below in reference to FIG. 5, the device 15 cancontain logic including device drivers that are to be made available tothe terminal 14.

FIG. 2 shows one preferred embodiment of the interface device 12. Asshown, the device 12 can include a first computer communicationinterface component, such as a PCMCIA card 20, which defines a firstinterface format. Also, the device 12 includes a second computercommunication interface component such as a universal serial bus (USB)connector 22 which defines a second interface format. In one preferredembodiment, the USB connector 22 includes a male USB “A” plug 24 havingtwo rows of pins (five pins in one row and four in the other row), withthe USB “A” plug 24 being connected via a cord 26 to a USB “B” plug 28.The USB plugs 24, 28 are preferably in accordance with USB 2.0. Inalternate embodiments, the second computer communication interfacecomponent can be established by a so-called “ILink” connection inaccordance with IEEE standard 1394 or even a wireless component such asa so-called “Bluetooth” rf communication device.

In any case, as intended by the present invention both computercommunication interface components are electrically associated with atransceiver 30, such as a wireless IP transceiver provided by Arraycomm.Such a transceiver operates in a frequency range of between ninekiloHertz to fifty gigaHertz (9 kHz-50 gHz) and more preferably in arange between two thousand three hundred million Hertz and two thousandthree hundred ten million Hertz (2300 mHz-2310 mHz). It is to beunderstood that the transceiver 30 can be integral to the PCMCIA card20. The transceiver 30 with PCMCIA card 20 establish a housing 32 thatcan include a raised hub 34 detachably supporting a preferablydirectional antenna 36.

As shown in FIG. 2, a USB “B” receptacle 38 is formed in the hub 34.Accordingly, the USB “B” plug 28 of the USB connector 22 is configuredfor mechanically and electrically engaging the receptacle 38. Thus, theUSB connector 22 is detachably engaged with the housing 32, but anon-detachable connection can also be used. According to presentprinciples, the transceiver 30 is associated with the antenna 36, suchthat both computer communication interface components are electricallyconnected to the antenna 36. It may now be appreciated that the PCMCIAcard 20 can be engaged with a PCMCIA slot of the user terminal 14 toestablish wireless communication between the user terminal 14 and thebase station 16 using the first interface format, or, if no PCMCIA slotis available, the USB “A” plug 24 can be engaged with a USB receptacleof the user terminal 14 to establish wireless communication between theuser terminal 14 and the base station 16 using the second interfaceformat.

FIG. 2 shows that if desired, a rechargeable battery 40 can be includedwith the housing 32. Also, one or more light emitting diodes (LED) 42can be mounted on the housing 34 to indicate whether the transceiver 30is communicating with the base station 16, and/or to indicate a lowvoltage condition of the battery, and/or to indicate other events suchas power on and so on. Still further, a small audio speaker or beeper 44can be mounted on the housing to indicate these same or differentconditions. It is to be understood that the user terminal 14 canalternatively provide such audible and/or visual indications.

To provide for recharging the battery 40, a charger port 46 configuredfor receiving a charger plug (not shown) can be formed in the housingand electrically connected to the battery 40. To conserve battery power,a power switch 48 can be provided on the housing 32 and electricallyconnected to the battery 40 so that a user can selectively connect anddisconnect the battery 40 from the remainder of the components in thehousing 32.

The chipsets, firmware, or software of the user terminal 14 areconfigured for operating with the interface device 12. The flow chartsherein illustrate the structure of a logic device of the presentinvention as embodied in computer program software. Those skilled in theart will appreciate that the flow charts illustrate the structures oflogic elements, such as computer program code elements or electroniclogic circuits, that function according to this invention. Manifestly,the invention is practiced in its essential embodiment by a machinecomponent that renders the logic elements in a form that instructs adigital processing apparatus (that is, a computer) to perform a sequenceof function steps corresponding to those shown. Internal logic could beas simple as a state machine.

In other words, the present logic may be established as a computerprogram that is executed by a processor as a series ofcomputer-executable instructions. In addition to residing on hard diskdrives, these instructions may reside, for example, in RAM of theappropriate computer, or the instructions may be stored on magnetictape, electronic read-only memory, or other appropriate data storagedevice.

FIG. 3 shows that the user terminal 14 can determine, at decisiondiamond 50, whether the interface device 12 is engaged with the terminal14. If not, the logic ends at state 52, but otherwise the logic flows todecision diamond 54 to determine whether the PCMCIA card 20 has beenengaged with a PCMCIA port on the terminal 14. Of course, for terminalsthat have no PCMCIA port, the step at decision diamond 54 is skipped.

When it is determined that the PCMCIA card 20 has been engaged with theterminal 14, a PCMCIA software driver module is invoked at state 56. Onthe other hand, when it is determined that the device 12 is engaged withthe terminal 14 but not via a PCMCIA connection, the logic flows toblock 58 to identify the format (e.g., USB) and thence to block 60 toinvoke the appropriate software driver module.

Once the interface device 12 has been engaged with the user terminal 14,the logic of FIG. 4 can be invoked. Commencing at block 62, an iconrepresenting the device 12 can be placed on the toolbar of the displayof the user terminal 14. As mentioned above, at block 64 the display ofthe terminal 14 can indicate link status, battery 40 status, device 12power on status, link signal strength, and so on. Audible feedback ofthese parameters can also be provided by the user terminal 14 at block66.

FIG. 5 shows the set up logic of the present system. Commencing at block70, the above-described dual interface device 12 is obtained. Moving todecision diamond 72 it is determined, with the device 12 installed inthe user terminal 14, whether a wireless IP signal is being received atthe user terminal 14. After the below-described driver installation, itis expected that a positive test will be obtained at decision diamond72, in which case the logic proceeds to block 74 to undertake routinecomputer housekeeping functions, e.g., battery charges, logging on, etc.The test for whether a signal is maintained can be repeated at decisiondiamond 76, and if persistent signal loss occurs the user can beprompted to contact system 10 customer service at block 78. Otherwise,the user can operate the user terminal 14 in accordance with the logicof FIG. 4 above.

In contrast, prior to loading software drivers for the two interfacesonto the user terminal 14, the test at decision diamond 82 will benegative, in which case the logic flows to block 82 wherein a CD such asthe program product 15 (FIG. 1) containing all necessary driverspreferably for all operating systems is engaged with the user terminal14, if necessary using a PCMCIA slot in accordance with principles knownin the art. Then, a set up screen can be presented at block 84 whichpreferably has a simple prompt, such as “load drivers now?” Theresulting user input to commence the load process is received at block86.

In accordance with the present invention, the logic then proceeds toblock 88, to automatically detect what operating system is present onthe user terminal 14. This can be undertaken in any one of a number ofways, such as by scanning an operating system file header or by someother method.

In any case, once the type of operating systems has been detected, thelogic creates a dual interface device driver directory at block 90, andthen at block 92 the PCMCIA and USB drivers from the CD are copied intothe directory. The CD preferably contains all PCMCIA and USB drivers forall anticipated operating systems, but in a preferred embodiment onlythe PCMCIA driver and USB driver that are tailored for the operatingsystem detected at block 88 are copied into the driver directory atblock 92. It may now be appreciated that owing to the present logic, theuser is not required to know what operating system is used by the userterminal 14 or to know what particular drivers must be loaded into thedriver directory.

If desired, certain terminal diagnostic monitoring can be executed andresults presented at block 94 to indicate, e.g., whether the driverswere successfully loaded onto the user terminal 14. If the user terminal14 has only a single PCMCIA slot by which the CD is connected to theterminal, a user prompt to remove the CD from the slot can be presentedon the display of the terminal 14 at block 96. The dual interface device12 is then engaged with the user terminal 14 at block 98 in accordancewith the disclosure above, and the operating logic of FIG. 3 invoked atblock 100.

While the particular SET UP LOGIC FOR DUAL INTERFACE WIRELESS IPCOMMUNICATION DEVICE as herein shown and described in detail is fullycapable of attaining the above-described objects of the invention, it isto be understood that it is the presently preferred embodiment of thepresent invention and is thus representative of the subject matter whichis broadly contemplated by the present invention, that the scope of thepresent invention fully encompasses other embodiments which may becomeobvious to those skilled in the art, and that the scope of the presentinvention is accordingly to be limited by nothing other than theappended claims, in which reference to an element in the singular means“at least one”. All structural and functional equivalents to theelements of the above-described preferred embodiment that are known orlater come to be known to those of ordinary skill in the art areexpressly incorporated herein by reference and are intended to beencompassed by the present claims. Moreover, it is not necessary for adevice or method to address each and every problem sought to be solvedby the present invention, for it to be encompassed by the presentclaims. Furthermore, no element, component, or method step in thepresent disclosure is intended to be dedicated to the public regardlessof whether the element, component, or method step is explicitly recitedin the claims. No claim element herein is to be construed under theprovisions of 35 U.S.C. §112, sixth paragraph, unless the element isexpressly recited using the phrase “means for”.

1. A user terminal for providing wireless IP communication using aninterface device having at least first and second communicationinterfaces, comprising: at least one operating system; and a computerprogram determining a type of the operating system without receiving anyuser input indicating the type and in response automatically loading atleast first and second device drivers associated with the first andsecond communication interfaces without any user input regarding drivertypes, the program determining which interface is engaged with theterminal and in response selecting which of the drivers to invoke. 2.The terminal of claim 1, wherein the program automatically establishes adevice directory using the operating system prior to loading thedrivers.
 3. The terminal of claim 2, wherein the program provides a userset-up prompt to the user.